fixes #768

server-functions are inconsistent between server renders and client renders.

When the server does a render server$ is directly invoked

/**
*  currently in the context of the server render you can basically think this as const fn = () => new Data()
*/
const $$server_module0$1 = server$.createHandler(async function $$serverHandler0() {
  return new Date();
}, "/_m/0dbe216f23/routeData", true);
server$.registerHandler("/_m/0dbe216f23/routeData", $$server_module0$1);

and on the client server$ is a fetch to the generate endpoint

/** 
* again you can think of this as const fn = () => fetch('/_m/0dbe216f23/routeData')
*/
const $$server_module0$1 = server$.createFetcher('/_m/0dbe216f23/routeData', false)

So when the server does a SSR render you get a raw Date object back from the server function while on the client its over a network boundary so it gets serialized by the server function middleware. This causes issues when returning none serializable object like Date where on the server you can call toLocaleDateString and get a successful first render but when the client navigates to the page it throws

TRPC went though a similar issue with their types trpc/trpc#3261 and what this PR is based on

• Make server-functions consistent between client and server
• update types
  • server$
  • createServerData$
  • createServerAction$
  • createServerMultiAction$
• How does this effect customer seralizers